Date: Tue, 12 Jul 94 04:30:20 PDT From: Ham-Digital Mailing List and Newsgroup Errors-To: Ham-Digital-Errors@UCSD.Edu Reply-To: Ham-Digital@UCSD.Edu Precedence: Bulk Subject: Ham-Digital Digest V94 #229 To: Ham-Digital Ham-Digital Digest Tue, 12 Jul 94 Volume 94 : Issue 229 Today's Topics: New IP Address when Moving? Send Replies or notes for publication to: Send subscription requests to: Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Ham-Digital Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/ham-digital". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Tue, 12 Jul 1994 00:41:45 GMT From: iglou!gregl.slip.iglou.com!ke4dpx@uunet.uu.net Subject: New IP Address when Moving? To: ham-digital@ucsd.edu In article <2vbfrs$6gs@info2.rus.uni-stuttgart.de> smiller@intelsun.rus.uni-stuttgart.de (Shannon Miller) writes: >Here's a question for which I can't seem to get a straight answer: >I got a TCP/IP address allocated to me when I lived in Oregon and >operated as N7APC. Now I live in Germany and operate as DL6SEU. >To get on the air with TCP/IP quickly I simply made use of my old >IP address. The question: -should- I get a "local" (German) IP >address? In any event I want to keep my original IP address as I >plan to return to the U.S. someday. >My Oregon IP address works fine of course, and shouldn't be in use >by any other station on the planet (since N7APC is off the air as >long as I'm here!), but one can easily tell that I'm not in the >same "subnetwork" as the locals. >Many thanks, >--Shannon, DL6SEU/N7APC I suggest getting a new, local IP address if you are going to be there for the long term. At the moment we really don't have so much need for organized addressing due to the lack of IPers in most areas. This is like to change in the near future and at that time maintaining a localized address will be critical to maintaining clean routes. I and the local TheNet nodes don't have to keep two dozen entries in the routing tables because we know all 44.106.56.xx addresses go this way and 44.106.3.xx addresses go that way. Simplification sure helps keep the routing tables in check. :-) You moving into the area with a non-local address could have significant impact on your ability to be heard. Routers in your immediate area may add a route specifically for you, but what about routers down the line? They don't recognize the odd address so you won't be able to get traffic beyond a certain point. The routers in my area, for example, easily handle new addresses of the form 44.106.56.xx and 44.106.3.xx. If you move in with an address outside this range, you won't be recognized and nobody will be able to get to you. ============================================================================ 73 de Greg AMPRNet - ke4dpx@ke4dpx.ampr.org [44.106.56.35] AX.25 - ke4dpxg@wi9p.#ncky.ky.usa.noam Internet - gregl@iglou.com ============================================================================ ------------------------------ End of Ham-Digital Digest V94 #229 ******************************